-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUGFIX beta] Use args proxy for modifier managers. #19163
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rwjblue
force-pushed
the
modifier-args-proxy
branch
3 times, most recently
from
September 28, 2020 14:33
ec868d1
to
9a90d5d
Compare
rwjblue
force-pushed
the
modifier-args-proxy
branch
from
September 28, 2020 18:07
9a90d5d
to
2226914
Compare
Generalizes the args proxy for use in both components and helpers. This does change the semantics slightly of `positional` arguments for component managers, notably it would make it so using computed properties with them would require a bit more work from custom component managers. The new semantics are more inline with the future of Ember, but if there many custom managers that use positional args we may want to reconsider this change. Co-authored-by: Robert Jackson <[email protected]>
Prior to this change, all custom modifiers **always** consumed every argument on install/update/destroy. This was because `reifyArgs` specifically reads all of them, and the actual usage was not consumption based. After this change, any modifiers using `modifierCapabilities('3.22')` will only consume the arguments that are actually used (named and positional). All modifiers that use `modifierCapabilities('3.13')` are unchanged (preserving backwards compatibility).
rwjblue
force-pushed
the
modifier-args-proxy
branch
from
September 28, 2020 18:13
2226914
to
d7f56c4
Compare
I've pulled in the changes from #19160 so we should be able to easily rebase that on top of these changes once this lands. |
rwjblue
changed the title
[BUGFIX lts] Use args proxy for modifier managers.
[BUGFIX beta] Use args proxy for modifier managers.
Sep 28, 2020
pzuraq
approved these changes
Sep 28, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for doing this!
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 15, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163 Ember apps < 3.22 are unaffected. This also adds Ember Try support for LTS 3.8 through 3.20
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 16, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163 Ember apps < 3.22 are unaffected. This also adds Ember Try support for LTS 3.8 through 3.20
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 18, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-render-modifiers
that referenced
this pull request
Oct 19, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 20, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22. This is only a breaking change for Ember 3.22+. Ember < 3.22 is unaffected. Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
NullVoxPopuli
added a commit
to NullVoxPopuli/ember-modifier
that referenced
this pull request
Oct 20, 2020
BREAKING CHANGE: destruction behavior changed to use new args proxy from 3.22 Resolves the issue described by: emberjs/ember.js#19162 fixed by: emberjs/ember.js#19163
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does two main things:
positional
arguments for component managers, notably it would make it so using computed properties with them would require a bit more work from custom component managers. The new semantics are more inline with the future of Ember, but if there many custom managers that use positional args we may want to reconsider this change.3.22
manager API version to ensure that custom modifier managers only consume the arguments that are actually used by the manager. In order for specific modifiers to take advantage of these changes, they need to be updated to usemodifierCapabilities('3.22')
(instead of3.13
).Fixes #19162